An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

Hello, Our iOS app has been rejected four times under Guideline 2.1(a) because sign-in fails on the review iPad. The latest rejection showed NSURLErrorDomain error -1001 (the request timed out) on an iPad Air 11-inch (M3) with iPadOS 27.0, on November 5, 2026, at about 11:54 UTC. The same happened on October 16, 2026. Setup: API: https://wp.pavilion.az, HTTPS on port 443, fixed DNS name DNS and proxy on Cloudflare (IPv4 and IPv6), publicly trusted certificate The app uses URLSession, with no custom certificate checks and no proxy settings What we checked: Neither our origin server nor Cloudflare logged any request from the review device on either day. Other clients were served normally during the same minutes. The domain resolves normally from many public DNS resolvers in the United States and Europe, over IPv4 and IPv6. The app signs in in under one second on an iPad simulator in a data center in Los Angeles, and on our own devices through TestFlight. This looks similar to https://developer.apple.com/forums/thread/773444, where a Cloudflare-hosted domain resolved to a wrong address inside Apple's network. Could someone from Apple check how wp.pavilion.az resolves, and whether it is reachable, from the App Review network? We have resubmitted a build that adds a short network check to the error message (the DNS result and which connection step fails), but each review cycle takes many days. Thank you.

Our first submission has now been rejected under Guideline 2.1(b), with the message: "the in-app purchases do not load successfully." Each review was performed on an iPad Air 11-inch (M3) running iPadOS 26.6. The app sells only auto-renewable subscriptions. We cannot reproduce the failure, and we have verified every part of the configuration we can think of. WHAT WE VERIFIED (via the App Store Connect API, not just the UI) Two subscriptions in one group, state READY_TO_SUBMIT Product IDs exactly match what the app requests Available in 175 territories, including the United States Prices set, en-US localizations present for both products and for the group App review screenshots attached to both, state COMPLETE Both subscriptions are included in the review submission (READY_FOR_REVIEW) Paid Apps Agreement: Active. Bank account: Active. Tax forms: Active. WHAT WORKS On our own devices, installed via TestFlight (sandbox environment), the products load correctly and a purchase completes and activates as expected. This works on both a real Apple ID and a Sandbox Tester account. WHAT WE OBSERVED FROM THE REVIEW SESSION We use RevenueCat. Their server-side API returns our offering with both packages and the correct product identifiers, so the offering metadata is fine. Our backend also shows that the reviewer's session reached our servers and signed in successfully at the review timestamp, so the device had working network connectivity. That leaves StoreKit itself returning no products on the reviewer's device, which is what empties the offering. QUESTIONS Are there known conditions under which StoreKit returns no products in the App Review sandbox for subscriptions that are in "Ready to Submit" and are attached to the same submission as the binary? For an app that has never been approved, is product loading during review handled differently from a normal sandbox session on a released app? Is there any way to obtain diagnostics from a review session, or to ask the reviewer for a screenshot of the failing screen? Replies in Resolution Center so far have only repeated the original rejection text. Is there anything specific to iPadOS 26.6 that could affect StoreKit 2 product lookups? For the next submission we have added a timeout and automatic retries around the product lookup, plus a visible retry control instead of a spinner, in case the failure is a transient cold-start timeout. But we would rather understand the actual cause than keep guessing. Any pointers appreciated.

Hello Apple Developer Community, My first iOS app, PitCaptain, has been stuck in “Waiting for Review” since October 7, 2026. App: PitCaptain Version: iOS 1.0.0 (build 10) Submission date: October 7, 2026 Current status: Waiting for Review Expedited review: Requested Contacted Apple Support: Yes The app has not moved to “In Review”, and I have not received any feedback or requests for additional information. PitCaptain helps endurance racing teams plan driver changes, driving stints, refuelling windows and driver-change alarms. I understand that review times can vary, but nine days without any status change is concerning, especially after requesting an expedited review. Could someone from App Review please check whether the submission is progressing normally or whether it may be stuck in the review queue? Any advice or assistance would be greatly appreciated. Thank you!

Days and Days of Apple Review Delays — For Us, This Is Business, Not a Game! Sorry, Other Platforms Do It Better! We are deeply disappointed and frustrated by Apple's prolonged App Review process and the lack of effective communication and support. Developing applications is not a game. It is business. Behind every app there are professionals, investments, deadlines, commitments and projects that cannot remain on hold indefinitely. Apple offers telephone assistance to customers purchasing an iPhone, yet developers facing critical App Review issues often struggle to speak directly with someone capable of resolving them. How is it possible that a company of Apple's size cannot provide accessible, qualified telephone support to the professionals who contribute to its ecosystem? A simple conversation could resolve in minutes what currently takes days of emails, support tickets and repeated submissions. Equally frustrating is the practice of communicating review issues one at a time, across multiple review cycles, rather than providing a comprehensive list of concerns whenever possible. This fragmented approach wastes everyone's time, creates unnecessary delays and offers no meaningful solution. In our case, despite promptly addressing every request and receiving approval for an expedited review, our application remains in "Waiting for Review" as of November 13, 2026, without any substantive explanation or response to our repeated requests for assistance. And the consequences are real. We were forced to postpone our official launch, scheduled for November 11, 2026, disrupting months of preparation, promotional activities, editorial planning and professional commitments. Our application is already available on Android and other digital app stores. Apple's App Store is the only major distribution channel where our application is still missing. Our experience with these other platforms has been considerably more straightforward and cooperative. It is particularly frustrating that Apple, a global leader in technology, is the only platform preventing us from completing our planned digital launch. We fully respect Apple's quality and security standards. However, high standards should never become an excuse for inefficient communication or inadequate developer support. We are not asking for special treatment. We are asking for transparency, timely assistance and respect for the professional work carried out within Apple's ecosystem. And what exactly is Apple keeping on hold? Radio Quadraro, a new independent, nonprofit radio station based in Rome, created by professionals passionate about music, broadcasting and communication. Our application has one simple purpose: to allow people to listen to our radio station. Yet an entire radio launch has been postponed while we wait for an App Store review. Behind every application there is a real project. Behind every delay there are real consequences. We did not expect Apple to make an exception for us. We expected Apple to live up to its own standards. We request an immediate update, confirmation of our expedited review status and direct assistance from a qualified Apple representative. Radio Quadraro Team App ID: 6823630759 Apple Developer Support Case: 30000007065025

Hello, My first app (Apple ID: 6770062707), submitted on the 29th of october, was rejected on November 6 under Guideline 3.1.1. I resolved the issue by removing the external donation link and submitted a new build on November 7, together with an expedited review request. Since then, the submission has remained in "Waiting for Review" for more than 6 days, with no updates. I have also contacted App Review via the Contact Us form, but have not received a response. Submission ID: 7e55dc6a-55b7-4742-b699-5531d38f1a3e Version: 1.0 (48) Could someone from App Review please check whether anything is blocking this submission? Thank you, Zoltán Hidegkuti

Hi, I’m building a free educational ear-training app for social dancers (Education category, no ads, no in-app purchases). In this dance tradition, recognising the orchestra by ear is a practical skill, not trivia. Each historical orchestra has its own rhythm, phrasing and character, and dancers adapt their movement to it: crisp and rhythmic for one, smooth and flowing for another, with dramatic pauses for a third. At social dance events, the music is played in sets by a single orchestra, so identifying it in the first seconds tells dancers how to move. This skill cannot be learned from text, notation or descriptions alone. It is acquired only by listening to the actual recordings and repeatedly practising recognising them, which is why authentic audio is essential. Teachers train this skill in class, and the app makes it practicable at home. Users learn through a catalogue of orchestras with style descriptions (what to listen for and how it affects the dance), A/B listening comparisons and short exercises with spaced repetition. After each answer the app explains which musical features identify the orchestra. As listening material, the app plays the official 30-second previews from the iTunes Search API: streamed only, never downloaded, saved or cached, each preview shows “provided courtesy of iTunes”, each preview has the official “Listen on Apple Music” badge linking to the exact recording, so users can listen to the full track and add it to their library, previews are never used as background music. The Search API terms say previews may be used “only to promote store content and not for entertainment purposes”. Is an educational exercise like this acceptable promotional use under these terms, or is MusicKit required for this kind of app? Apple Developer Support (case 103008374208) suggested I ask here. Thank you!

Hello App Review team, I'm asking for help confirming that our escalated case is attached to our current submission. App: Upfora (iOS) App ID: 6812258703 Version: 3.4 Current submission: November 8, 2026, "Waiting for Review" since then Developer Support case: 102994003655 Background - First submitted September 15, 2026. This is our first App Store release; the app is already live on Google Play and on the web. - App Review has reviewed it twice: October 1 (demo login not working) and October 22 (reporting of user-generated content). Both issues were fixed and resubmitted the same day. - In between, we withdrew and resubmitted several times to ship fixes. I now understand that each resubmission reset our place in the queue, and that this accounts for much of the delay. That was our mistake. Current situation - Developer Support escalated our case in early November, while our October 31 submission was waiting. We then resubmitted on November 7 and November 8, before I understood the effect, so I'm concerned the escalation is tied to a submission that no longer exists. - We have made no changes since November 8 and will make none until the review is complete. - The demo account in the review notes is active, and the reporting feature requested in the last review is included in this build. My questions 1. Can the escalation on case 102994003655 be applied to the current November 8 submission? 2. Is there anything on our side (metadata, review notes, account) that is holding the submission? Thank you for your help. Nodirkhon Founder, Upfora

Hi everyone, My app has been stuck in "In Review" since November 1, 2026. It's been 12 days now with no updates or communication from Apple. The app hasn't been rejected and Apple hasn't reported any issues or requested any changes. I'm just waiting for the review to finish. I've also checked my app analytics and there has been no activity from reviewers since the app entered "In Review". I understand that not all review activity may be visible in analytics, but it makes me wonder if anyone has actually started reviewing it. I've contacted Apple Developer Support several times and even opened a new support ticket, but I still haven't received a response that addresses the issue. What's strange is that another app on the same developer account entered review on November 11 and was approved the same day. Has anyone else experienced something like this? Is there any other way to reach the App Review team or get someone to look into a stuck review? Any help would be appreciated. Thanks!

My first app, Now We Pray – In Jesus’ Name (iOS 1.0, with one non-consumable in-app purchase), has been in “Waiting for Review” for over a month. Submitted October 10, 2026. October 13: received Guideline 2.1 “Information Needed”; answered the same day with a screen recording and full answers, and the status returned to “Waiting for Review”. October 31: after three weeks with no movement, I removed it from review and resubmitted with an updated name and icon. It has been “Waiting for Review” since then (13 days). The demo account in the App Review notes has never been signed into since October 13, so the review has not started. I have contacted App Review through Contact Us, requested an expedited review, and phoned Developer Support, who told me nothing is wrong and to wait. Agreements, tax and banking are all active. Is there anything on my side that could be holding this submission back, or anything further I should do? I’m happy to send the submission ID to Apple staff. App Apple ID: 6820688153 Submitted: Waiting for Review since Oct 31, 2026 at 2:53 PM

Hi, My app's first version has been in "Waiting for Review" since October 28, 2026, 12:11 PM. App: Helium – Squeaky Voice Changer Apple ID: 6825700812 Submission ID: a49a4eaa-acd9-4c90-ba74-2efd935a8c15 Build: 1.0 (4) App Review sent feedback on October 23 and October 27. I addressed every point (App Tracking Transparency implementation, third-party AI clarification, face data questions), replied in App Store Connect and resubmitted on October 28. I also submitted an expedited review request. The message thread is now locked, so today I updated the App Review Information notes to confirm that build 4 is the build under review and to explain where the ATT prompt appears. Could someone from App Review check whether anything else is needed from my side? Thank you.

I’m an individual developer with a live educational app for children aged 3 to 5 who can’t read yet. Everything in the app is spoken: instructions, feedback and task prompts are voice recordings. For a child who can’t read, the language isn’t a setting. It is the whole product. Current setup The app is Sovice, Croatian, live since October 2026, with native Croatian voice recordings and a Croatian curriculum. It’s currently Croatian only. I’m now preparing an English version for the US and UK. The problem with adding English to the same app The child can’t recover from the wrong language. With two languages in one app, a parent picking the wrong one, or the app ending up in one by accident, leaves a three-year-old who can’t read the screen to switch back. This applies both ways: a US child landing in Croatian and a Croatian child landing in English. The listing follows the device language, not the market. Many Croatian parents set their phones to English. With an English listing, they’d see an English app and miss that this is a Croatian app, even though the Croatian recordings are why they’d download it. The markets need different products. The English version would have a different curriculum (English phonics and early reading), its own brand and mascot, and features for US families, such as a homeschool parent mode. Croatian families need things US families don’t, and the other way round. What I’m considering Two separate single-language apps from one shared codebase, each with its own bundle ID, name, brand and content, and availability limited to its own markets: Sovice: Croatian, sold in Croatia and the region. Wise Beaks: English, sold in English-speaking countries. Questions Has anyone shipped separate language or market versions of a kids or education app without a 4.3(a) rejection? What differentiation did App Review accept? Does “the users can’t read, so each app must be single-language” help when explaining this to App Review, or is it irrelevant to 4.3(a)? If one app is the expected path: is there a way to show a specific product page per country regardless of device language?

Hello Apple App Review Team, I'm requesting assistance with an unusually prolonged App Review delay for our first iOS release. App:** ZiniGo® – Bhutan SimplifiedApp Apple ID:** 6805887247Version:** 1.0 (Build 4)Submitted:** November 3, 2026Current Status:** Waiting for Review Our previous submission remained in Waiting for Review from October 12 to November 3, approximately 22 days. We submitted a corrected Build 4 on November 3 and received confirmation on November 4 that Apple would expedite its review. However, as of November 13, the submission still has not entered In Review. We contacted Apple Developer Support on November 6 and followed up on November 12 under an existing support case. So far, we have received acknowledgment emails but no substantive response. The current build is validated, and we have addressed the previous Guideline 2.1(a) issues concerning account creation, OTP authentication, and incomplete content. Could an Apple App Review representative please investigate whether our submission is correctly queued for expedited review and whether any additional verification or documentation is required? We are not requesting another expedited review. We simply want to ensure that the existing submission is progressing correctly. Thank you for your assistance.

Sing Academy: Learn to Sing (Apple ID 6825501026), version 1.0 with three in-app purchases, was submitted on October 25 and has been Waiting for Review for 11 days with no messages. It's the first submission from this account, and all agreements, banking and tax are active. A status inquiry (case 103017295001) sent on November 2 has had no reply, and phone support shows as unavailable due to high call volumes. Could someone from App Review check whether the submission is queued correctly or needs anything from me?

Hello, Our iOS app has been "Waiting for Review" since 30 October, despite an expedited review that Apple confirmed was accepted. I'd appreciate any guidance from Apple staff or developers who have seen something similar. Timeline: 17 October: version 1.0 submitted. 20 October: expedited review requested and granted. 22 October: we found and accepted a pending update to the Apple Developer Program License Agreement. 27–28 October: reviewed and rejected (guidelines 4.3(b), 1.2, 2.3.6 and 2.1(b)). 28 October: we replied in App Store Connect with screen recordings and the requested information, and updated the age rating. 30 October: resubmitted. Status has been "Waiting for Review" since. 9 November: Developer Support confirmed the app is in the expedited review queue and that no further action is required from us. Our reply addressed each point: the requested safety features (terms acceptance, reporting and blocking) were already in the app and shown in screen recordings, the age rating was corrected, and we answered the business-model questions (the app is free with no purchases). We also responded to the 4.3(b) concern in detail. Questions: Is a wait of two weeks or more after a resubmission typical when the original rejection included 4.3(b)? Is there anything we can do to help the review proceed, or should we simply continue to wait? Case numbers, if useful to Apple staff: 102930345382 and 103006437930. Thank you.

Hello, Our new app has been in "Waiting for Review" for longer than usual, and we have not received any message in App Store Connect or by email: Sweet Cascade: Match 3 Puzzle (Apple ID 6832678740), version 1.0.0, submitted Nov 10, 2026 Our previous submissions were reviewed within 24–48 hours. Agreements, tax, banking and Digital Services Act information are all active, and there are no messages in the Resolution Center. We have not cancelled or resubmitted, so as not to lose our place in the queue. Could someone from App Review please check whether this submission is waiting on anything from us, or whether there is an issue with it? Thank you for your help.

Our app TSPhq (Apple ID 6830393818, iOS version 1.0, build 3) was submitted for review on 8 November 2026 and is still Waiting for Review. We requested an expedited review on 12 November and the form confirmed it would be expedited but the status has not changed... TSPhq is the internal staff app for a property styling company in Sydney and its staff start using it on Monday 16 November. We also submitted an unlisted distribution request for the app on 8 November. Could someone from App Review please check whether this submission is stuck?? Thank you.

Hello, I am investigating an intermittent In-App Purchase failure that occurred during App Review for the first release of my app. Environment Review device: iPad Air 11-inch (M3) OS: iPadOS 26.6 Environment: App Review sandbox Product type: Consumable StoreKit integration: RevenueCat through react-native-purchases 10.4.3 Observed behavior StoreKit successfully returned the products, localized names, and prices. The reviewer could see the credit packs and initiate the native purchase flow. My diagnostics show this sequence: Purchase initiated PURCHASE_CANCELLED; no transaction evidence Purchase initiated again RevenueCat code 2: STORE_PROBLEM elapsed: 9.4 seconds no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE elapsed: 0.6 seconds no transaction evidence code-block The relevant sanitized logs are: { "occurredAt": "2026-08-25T12:52:59.733Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "2", "providerReadableCode": "STORE_PROBLEM", "transactionEvidence": false, "elapsedMs": 9417 } code-block { "occurredAt": "2026-08-25T12:55:42.752Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "5", "providerReadableCode": "PRODUCT_NOT_AVAILABLE_FOR_PURCHASE", "transactionEvidence": false, "elapsedMs": 637 } code-block No App Store transaction was created, and therefore RevenueCat received no transaction or webhook for these attempts. Configuration verified I confirmed that: The affected product and the other consumable products are attached to the App Review submission. Product IDs match between the app, App Store Connect, and RevenueCat. Prices and localizations are configured. The products are available in the relevant storefronts. The Paid Apps Agreement is active. Banking and tax information are active. The In-App Purchase capability is present. The distribution build does not use a local StoreKit configuration file. The same build and affected product completed successfully afterward on a physical device using Apple Sandbox. The native purchase sheet opened, the transaction completed, and the consumable content was delivered successfully in my reproduction. The product metadata clearly remained available because its localized name and price were displayed. However, after the initial STORE_PROBLEM, subsequent purchase requests were rejected almost immediately as PRODUCT_NOT_AVAILABLE_FOR_PURCHASE. I do not have the underlying Apple NSError, such as an ASDServerErrorDomain or AMSErrorDomain value, because it was not exposed in my remote diagnostic record. Questions Can a failed sandbox transaction leave the StoreKit account/session or commerce-catalog state temporarily inconsistent, causing subsequent requests for an otherwise loaded product to return storeProductNotAvailable? Does StoreKit use separate metadata and transaction-eligibility services, allowing product information to load while the same product is rejected during purchase()? Are there known sandbox or StoreKit issues on iPadOS 26.6 that could produce this sequence? Could a stale App Review sandbox account token or storefront session explain the transition from STORE_PROBLEM to PRODUCT_NOT_AVAILABLE_FOR_PURCHASE? Is there any developer-side configuration that could explain this when the same product and binary complete successfully using another sandbox session? What additional logging should I capture from RevenueCat’s React Native SDK to preserve the complete underlying Apple error chain?

Hello App Review team, Our app eKhizmat (Apple ID: 6771045955) has been in "Waiting for Review" status since November 5, 8 days now, with no updates. We are a government agency, and the app is scheduled for an official public presentation in the coming days. The presentation date is fixed and cannot be moved. What we have done so far: Submitted an Expedited Review request We have not uploaded a new build, to keep our place in the queue. App Store Connect shows no messages or required actions from our side. We would be very grateful if you could check the status of this submission. We can provide a demo account or any additional information immediately. Thank you for your help.

Hello App Review team and fellow developers, I'm a solo developer in Korea, and Duedrop is the first app I've ever submitted. It has now been more than two weeks (16 days) since my first submission, and I haven't been able to get any response through the usual channels. I'd be very grateful for any help or advice. Here is the timeline: October 28: Submitted Duedrop version 1.0 for review. October 29: Received an information request from App Review and replied the same day with the requested details. October 30 – November 9: The status stayed "In Review" for about 10 days with no further messages. During that time, I submitted one expedite request and two status inquiries through the Contact Us form, but did not receive any reply. November 9: Since there was no progress, I removed version 1.0 from review and submitted version 1.0.1 (build 13). November 9 – today: Version 1.0.1 has been "Waiting for Review" for four days. Meanwhile, two other apps from the same developer account, submitted on November 11 and 12, have already been reviewed and approved. Because of this, I'm worried that Duedrop's submission may be stuck or held for a reason I'm not aware of. About the app, in case it helps: Duedrop is a calendar app that also lets users keep track of their own subscription payment dates and monthly spending. It does not process any payments, connect to bank accounts, or require an account. All data stays on the user's iPhone, and in their own iCloud only if they turn on sync. Service icons are loaded from each service's public website icon and are not bundled in the app. Prices shown when adding a subscription are labeled as examples, and users can edit them freely. In-app purchases are a one-time premium unlock and optional tips that do not unlock any features. If anything is missing or needs to be changed, I would be happy to fix it right away. I would truly appreciate it if someone could check the status of this submission. Thank you very much for your time.

Hello App Review team, Our app has been in “Waiting for Review” since November 4, 2026, and we have not received any update. App name: WAIIS 2026 Apple ID: 6827532313 Bundle ID / SKU: com.sipod.waiis Submitted: November 4, 2026, 1:49 PM Developer Support Case ID: 30000012162555 We submitted an expedited review request and followed up twice by email, but have not received a response. The release is time-critical: this is the official app for a conference starting on Monday, November 16, 2026, with over 2,000 registered attendees. Attendees will use the app for the event schedule, check-in and networking, and we need to send them the download link before the weekend. If the app is not approved by Friday, November 13, attendees will not have it when the event opens. Could you please check whether this submission is stuck and, if possible, escalate it? We are available by phone at any time to provide whatever the reviewer needs. Thank you, Dejan Bečirić, Sipod Software